Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4b79e891e26a2a147cd0948db6286dc65f3b6d036bbf7b6c8e91aaf2a1c10f3

Tx prefix hash: 0ce43e3b9d70eed6ca5dfd9a50a5305cbb5319ccb17f23ef4d5998499660d733
Tx public key: 131e03dfc46e64cab8868df4e86f07188b09b44aff200d271169ffb10d195dd0
Timestamp: 1782743259 Timestamp [UTC]: 2026-06-29 14:27:39 Age [y:d:h:m:s]: 00:142:20:25:40
Block: 1570795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 111037 RingCT/type: yes/0
Extra: 01131e03dfc46e64cab8868df4e86f07188b09b44aff200d271169ffb10d195dd0

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 024e7fee2c14629a4f22c564d33e17fc64376c4a8529c3a74a3340192b18daa1 0.000600000000 2060775 of 15 <bb>

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": 1570805, "vin": [ { "gen": { "height": 1570795 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "024e7fee2c14629a4f22c564d33e17fc64376c4a8529c3a74a3340192b18daa1", "view_tag": "bb" } } } ], "extra": [ 1, 19, 30, 3, 223, 196, 110, 100, 202, 184, 134, 141, 244, 232, 111, 7, 24, 139, 9, 180, 74, 255, 32, 13, 39, 17, 105, 255, 177, 13, 25, 93, 208 ], "rct_signatures": { "type": 0 } }


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