Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 7f29d6721661c073598e2c8f3dc4fb73b127338c1455257d96f6c8a41d5866a0

Tx prefix hash: 5228c441623cab1b9f17b4b4ff431bda5c7af407326aa405d034b9c3a11dfccc
Tx public key: 5a8318ba20e56f2db1dc10d7f1934820999857cdc8aa900baf3d47b241d6675e
Timestamp: 1720437932 Timestamp [UTC]: 2024-07-08 11:25:32 Age [y:d:h:m:s]: 01:312:05:31:35
Block: 1061195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474046 RingCT/type: yes/0
Extra: 015a8318ba20e56f2db1dc10d7f1934820999857cdc8aa900baf3d47b241d6675e02110000001ee914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ae629741a632f7dae84d17af7c626d3e7d7a80da335cf3fa6a445784d55d1702 0.000600000000 1531686 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1061205, "vin": [ { "gen": { "height": 1061195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae629741a632f7dae84d17af7c626d3e7d7a80da335cf3fa6a445784d55d1702" } } ], "extra": [ 1, 90, 131, 24, 186, 32, 229, 111, 45, 177, 220, 16, 215, 241, 147, 72, 32, 153, 152, 87, 205, 200, 170, 144, 11, 175, 61, 71, 178, 65, 214, 103, 94, 2, 17, 0, 0, 0, 30, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: