Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8960ed79278a982bdfc67d654bd48efc9f240b38c6c90f0acf1edb53e036aef6

Tx prefix hash: c326fbd7710b3669124b9666661b9babd2203601d55e07dbb10832f9e22daa33
Tx public key: befb6d32207a9c8e61db1bcddef428c5fbea86cff7bbdd016965347255b57efd
Timestamp: 1699129143 Timestamp [UCT]: 2023-11-04 20:19:03 Age [y:d:h:m:s]: 01:191:03:37:27
Block: 884780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397588 RingCT/type: yes/0
Extra: 01befb6d32207a9c8e61db1bcddef428c5fbea86cff7bbdd016965347255b57efd021100000001faf35c9c000000000000000000

1 output(s) for total of 0.718383876000 dcy

stealth address amount amount idx
00: a36a0e385f81db4e236b4c151e29ec43a3e3845552a385b39a1616c3ab5b3c0b 0.718383876000 1340527 of 0

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": 884790, "vin": [ { "gen": { "height": 884780 } } ], "vout": [ { "amount": 718383876, "target": { "key": "a36a0e385f81db4e236b4c151e29ec43a3e3845552a385b39a1616c3ab5b3c0b" } } ], "extra": [ 1, 190, 251, 109, 50, 32, 122, 156, 142, 97, 219, 27, 205, 222, 244, 40, 197, 251, 234, 134, 207, 247, 187, 221, 1, 105, 101, 52, 114, 85, 181, 126, 253, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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