Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1cb6690d9102ec14622e2e5826c4f44f7e0c9e1392aa905e8c80a4874c3f479

Tx prefix hash: bd4abef29827d48bb146c62530b7028477729e1a6797fc0ea9506423384ad9bf
Tx public key: 96b7051f24257b8bb6d4957bba97f8ab3af0d3a9bffec0a2478830f7725b96c0
Timestamp: 1737127892 Timestamp [UCT]: 2025-01-17 15:31:32 Age [y:d:h:m:s]: 00:337:18:13:21
Block: 1199400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238952 RingCT/type: yes/0
Extra: 0196b7051f24257b8bb6d4957bba97f8ab3af0d3a9bffec0a2478830f7725b96c0021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c459fecb4ab09f4c07ea2af6e2d969d385cf189b1d5faf880a8a029b391881c 0.600000000000 1686031 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": 1199410, "vin": [ { "gen": { "height": 1199400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c459fecb4ab09f4c07ea2af6e2d969d385cf189b1d5faf880a8a029b391881c" } } ], "extra": [ 1, 150, 183, 5, 31, 36, 37, 123, 139, 182, 212, 149, 123, 186, 151, 248, 171, 58, 240, 211, 169, 191, 254, 192, 162, 71, 136, 48, 247, 114, 91, 150, 192, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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