Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfb16a03b7fafb6b6bc704535a5bebd84cac2b1a2f172a205764769829b4d4af

Tx prefix hash: 9a50c4332273f0e0e44ad207f46646375183ea82e37ff0ccb1b9fc9ef4c1da0b
Tx public key: d34e1140d6d0aded8d45ff637b4255985ba6f9b90b288365899276bd7299c679
Timestamp: 1748760763 Timestamp [UCT]: 2025-06-01 06:52:43 Age [y:d:h:m:s]: 00:173:10:56:11
Block: 1295461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121643 RingCT/type: yes/0
Extra: 01d34e1140d6d0aded8d45ff637b4255985ba6f9b90b288365899276bd7299c679021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6a38241d4c25fd914e4e0e6aa61b76fc72ee91e621e1fec915961028065b78b 0.600000000000 1782964 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": 1295471, "vin": [ { "gen": { "height": 1295461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6a38241d4c25fd914e4e0e6aa61b76fc72ee91e621e1fec915961028065b78b" } } ], "extra": [ 1, 211, 78, 17, 64, 214, 208, 173, 237, 141, 69, 255, 99, 123, 66, 85, 152, 91, 166, 249, 185, 11, 40, 131, 101, 137, 146, 118, 189, 114, 153, 198, 121, 2, 17, 0, 0, 0, 6, 191, 81, 178, 162, 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