Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87f4f3bab6fe1552aea1ca36daa964e6ed038e73ea350268397bf2a38d7fb121

Tx prefix hash: ff63500edd995d73a879847a0fee019c0f7863dc4c618754c0498f0fe7a5e9d1
Tx public key: c54e66fbc1133ca31dde441b5794e2be3090fb8f405a17d6ca066aeec9e25139
Timestamp: 1730633735 Timestamp [UCT]: 2024-11-03 11:35:35 Age [y:d:h:m:s]: 00:148:04:57:22
Block: 1145631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105744 RingCT/type: yes/0
Extra: 01c54e66fbc1133ca31dde441b5794e2be3090fb8f405a17d6ca066aeec9e251390211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 817c7e0e075ff7ed14481890ae8dd170d92c5644917b9d179e7a67775c41cb8d 0.600000000000 1630114 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": 1145641, "vin": [ { "gen": { "height": 1145631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "817c7e0e075ff7ed14481890ae8dd170d92c5644917b9d179e7a67775c41cb8d" } } ], "extra": [ 1, 197, 78, 102, 251, 193, 19, 60, 163, 29, 222, 68, 27, 87, 148, 226, 190, 48, 144, 251, 143, 64, 90, 23, 214, 202, 6, 106, 238, 201, 226, 81, 57, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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