Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83b287d9f407ae334b8d9cb7af5ab6453a684099c7db65db21f53a4349656d29

Tx prefix hash: 1064aff2b80b62595004c70832584f9faffe86362052062d4d56a302496dc74f
Tx public key: f9211a40179951994ef4cdc2c0a6de2bf577eeb512ab5a5e32a0d97892a72aa8
Timestamp: 1736952112 Timestamp [UCT]: 2025-01-15 14:41:52 Age [y:d:h:m:s]: 00:309:13:36:12
Block: 1197947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218750 RingCT/type: yes/0
Extra: 01f9211a40179951994ef4cdc2c0a6de2bf577eeb512ab5a5e32a0d97892a72aa8021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d37a1dfbabec4a3191171094b668ce905c0515fdaf5ddf0a3b1765c4f559062a 0.600000000000 1684564 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": 1197957, "vin": [ { "gen": { "height": 1197947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d37a1dfbabec4a3191171094b668ce905c0515fdaf5ddf0a3b1765c4f559062a" } } ], "extra": [ 1, 249, 33, 26, 64, 23, 153, 81, 153, 78, 244, 205, 194, 192, 166, 222, 43, 245, 119, 238, 181, 18, 171, 90, 94, 50, 160, 217, 120, 146, 167, 42, 168, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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