Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb6d530d14f5013123eafce2fba4d5b5048601ed5324edceff72dccc1907a77d

Tx prefix hash: 08bc24b5ededa305f7b3fdef52013c9d82f6d14507a448d42b5d1b5b12171fe8
Tx public key: 0e5046a675f2613f967f8b6f973654e3d43fa46128e2f8c3105c8c3e02e54638
Timestamp: 1729469435 Timestamp [UCT]: 2024-10-21 00:10:35 Age [y:d:h:m:s]: 00:144:12:09:13
Block: 1136035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103092 RingCT/type: yes/0
Extra: 010e5046a675f2613f967f8b6f973654e3d43fa46128e2f8c3105c8c3e02e546380211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73db7cafd069194dc239576823ee8e8607d3b82cb8542cf174ac7c3633cd1409 0.600000000000 1619376 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": 1136045, "vin": [ { "gen": { "height": 1136035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73db7cafd069194dc239576823ee8e8607d3b82cb8542cf174ac7c3633cd1409" } } ], "extra": [ 1, 14, 80, 70, 166, 117, 242, 97, 63, 150, 127, 139, 111, 151, 54, 84, 227, 212, 63, 164, 97, 40, 226, 248, 195, 16, 92, 140, 62, 2, 229, 70, 56, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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