Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7f74252fc2df598b00d1ee25b03d2878ed3d5ca0938c18aa31c11c954a3b059

Tx prefix hash: 891f317937fc26c6163c946e7be395d0ffe7f41034c4d589191fc56a45e425d6
Tx public key: 1a14c15f200df1486c0fa4f5ad707a532efa7872384d6a973d6d5ed7f94f22a2
Timestamp: 1710455525 Timestamp [UTC]: 2024-03-14 22:32:05 Age [y:d:h:m:s]: 02:064:21:53:30
Block: 978449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 558480 RingCT/type: yes/0
Extra: 011a14c15f200df1486c0fa4f5ad707a532efa7872384d6a973d6d5ed7f94f22a202110000000552d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a9f0c97d5982507e6e582316d00d17d6ef0f9b2643060c53701f4c2bd2e91fd8 0.000600000000 1438476 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": 978459, "vin": [ { "gen": { "height": 978449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9f0c97d5982507e6e582316d00d17d6ef0f9b2643060c53701f4c2bd2e91fd8" } } ], "extra": [ 1, 26, 20, 193, 95, 32, 13, 241, 72, 108, 15, 164, 245, 173, 112, 122, 83, 46, 250, 120, 114, 56, 77, 106, 151, 61, 109, 94, 215, 249, 79, 34, 162, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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: