Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68bf9619f34aaaadf22b2cd4ef5c106384f07990a8d5b9701d76d1bd207dd5ed

Tx prefix hash: 4f7f9afadeb53ea453309bfe8a76a4e2411c2216a1a964b932cad96b8fdbc427
Tx public key: a8918a86df9b08ea468cf91dcd82184deedfde83c8d5a0672adf95fb440bdbf9
Timestamp: 1582064980 Timestamp [UCT]: 2020-02-18 22:29:40 Age [y:d:h:m:s]: 05:256:17:37:15
Block: 67754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1334284 RingCT/type: yes/0
Extra: 01a8918a86df9b08ea468cf91dcd82184deedfde83c8d5a0672adf95fb440bdbf90211000000344ac5aa02000000000000000000

1 output(s) for total of 366.019041124000 dcy

stealth address amount amount idx
00: 48175c64de9849f29dbfcf0e579acabb23b57f556aadbe31a2024412024af691 366.019041124000 124801 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": 67764, "vin": [ { "gen": { "height": 67754 } } ], "vout": [ { "amount": 366019041124, "target": { "key": "48175c64de9849f29dbfcf0e579acabb23b57f556aadbe31a2024412024af691" } } ], "extra": [ 1, 168, 145, 138, 134, 223, 155, 8, 234, 70, 140, 249, 29, 205, 130, 24, 77, 238, 223, 222, 131, 200, 213, 160, 103, 42, 223, 149, 251, 68, 11, 219, 249, 2, 17, 0, 0, 0, 52, 74, 197, 170, 2, 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