Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2453fb023c1220385185a8bf91c276b1a4e06297281dec480778cf6bf6ffa81

Tx prefix hash: de59f8f9b6cfa3873dccc20d8a36b16e912574906039d4e9192e1463866212d5
Tx public key: db90e32e3bd6f6a1b03c112bca533d33b025ba0bd48b492ef21c7791aa622d93
Timestamp: 1696705877 Timestamp [UCT]: 2023-10-07 19:11:17 Age [y:d:h:m:s]: 01:169:09:49:00
Block: 864637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382103 RingCT/type: yes/0
Extra: 01db90e32e3bd6f6a1b03c112bca533d33b025ba0bd48b492ef21c7791aa622d9302110000000575e3f0e9000000000000000000

1 output(s) for total of 0.837719696000 dcy

stealth address amount amount idx
00: 3820ca6114d70f7da3d12a3671a5573fae8dc8c1c1de4eb77a6cbccf35167b49 0.837719696000 1319157 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": 864647, "vin": [ { "gen": { "height": 864637 } } ], "vout": [ { "amount": 837719696, "target": { "key": "3820ca6114d70f7da3d12a3671a5573fae8dc8c1c1de4eb77a6cbccf35167b49" } } ], "extra": [ 1, 219, 144, 227, 46, 59, 214, 246, 161, 176, 60, 17, 43, 202, 83, 61, 51, 176, 37, 186, 11, 212, 139, 73, 46, 242, 28, 119, 145, 170, 98, 45, 147, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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