Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a361e67d9e0434232ed2a0b4f1f276b65c676042b04bd35ac09d312e51e2f27

Tx prefix hash: 04f4f2817d37ac0b5574fc6b86b03d056585d80c0dcad7d2d5292521425d3908
Tx public key: 6a355e6ed14e17b11c38f371ba9be51dc360a04993e5d0aedf718f2f188c2e53
Timestamp: 1747174871 Timestamp [UCT]: 2025-05-13 22:21:11 Age [y:d:h:m:s]: 00:191:16:18:39
Block: 1282317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134695 RingCT/type: yes/0
Extra: 016a355e6ed14e17b11c38f371ba9be51dc360a04993e5d0aedf718f2f188c2e530211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b1d8b7049dd4cddef7ec925e58a02df2d5d50d837f8ed18c3895ad6dc2411c2 0.600000000000 1769724 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 dinasty-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": 1282327, "vin": [ { "gen": { "height": 1282317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b1d8b7049dd4cddef7ec925e58a02df2d5d50d837f8ed18c3895ad6dc2411c2" } } ], "extra": [ 1, 106, 53, 94, 110, 209, 78, 23, 177, 28, 56, 243, 113, 186, 155, 229, 29, 195, 96, 160, 73, 147, 229, 208, 174, 223, 113, 143, 47, 24, 140, 46, 83, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8