Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c5cd5f579346d1a9b8499257a6d4ebf3697c3e892af14a201153588d7c413ce

Tx prefix hash: 8109d5b0a59f93d38a9eb4221dc11bbf740879ff47cb69bc7a7061115eec2431
Tx public key: 45b8fc7c0bda5ba6f268e912d75daaed42c69e1c902e4dc17bc5d26ef51cb7aa
Timestamp: 1734217452 Timestamp [UCT]: 2024-12-14 23:04:12 Age [y:d:h:m:s]: 00:100:04:03:26
Block: 1175333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71353 RingCT/type: yes/0
Extra: 0145b8fc7c0bda5ba6f268e912d75daaed42c69e1c902e4dc17bc5d26ef51cb7aa0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89750bae824e56fb3c0866160d28fa0aa3a2c61c3416a1522c12f5eb64a38758 0.600000000000 1661600 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": 1175343, "vin": [ { "gen": { "height": 1175333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89750bae824e56fb3c0866160d28fa0aa3a2c61c3416a1522c12f5eb64a38758" } } ], "extra": [ 1, 69, 184, 252, 124, 11, 218, 91, 166, 242, 104, 233, 18, 215, 93, 170, 237, 66, 198, 158, 28, 144, 46, 77, 193, 123, 197, 210, 110, 245, 28, 183, 170, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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