Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ce41cf4cc81bbbb41bb119092b21a37ec27580b5e013dee3a3376b92370e885

Tx prefix hash: fc5d75e1710725fd32aa8d09a5bc8ea4bfb7254a15b237744d87c6d0b49a1bd7
Tx public key: 2d09994f7e967a761199f5285338d8e261988743db22b44022cd3ea81758d915
Timestamp: 1731729064 Timestamp [UCT]: 2024-11-16 03:51:04 Age [y:d:h:m:s]: 00:007:18:06:51
Block: 1154712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5535 RingCT/type: yes/0
Extra: 012d09994f7e967a761199f5285338d8e261988743db22b44022cd3ea81758d9150211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b033a977946cbe93df9e77d344c4ca30e4e77f895ba595a0ba981e8e63b7dc1e 0.600000000000 1640325 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": 1154722, "vin": [ { "gen": { "height": 1154712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b033a977946cbe93df9e77d344c4ca30e4e77f895ba595a0ba981e8e63b7dc1e" } } ], "extra": [ 1, 45, 9, 153, 79, 126, 150, 122, 118, 17, 153, 245, 40, 83, 56, 216, 226, 97, 152, 135, 67, 219, 34, 180, 64, 34, 205, 62, 168, 23, 88, 217, 21, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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