Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ff4b9d82e4ecca3bb6aa8cb32001e1fe56e5ad072ef981c7923cc7faecd5707

Tx prefix hash: 72688baf29cbc20df3c57286431863b4f767a89c083c4fc00dc6310e8ff422a9
Tx public key: 6a7b214f4543655304bf163d212b9c23336416e03b3dbc15c18f583c7b29770e
Timestamp: 1708951813 Timestamp [UCT]: 2024-02-26 12:50:13 Age [y:d:h:m:s]: 01:272:17:29:55
Block: 965968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453665 RingCT/type: yes/0
Extra: 016a7b214f4543655304bf163d212b9c23336416e03b3dbc15c18f583c7b29770e0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d30d3fd8de4185a34d6fb625db558907a4909e6546af0cc569bfac3aebd65f8e 0.600000000000 1425723 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": 965978, "vin": [ { "gen": { "height": 965968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d30d3fd8de4185a34d6fb625db558907a4909e6546af0cc569bfac3aebd65f8e" } } ], "extra": [ 1, 106, 123, 33, 79, 69, 67, 101, 83, 4, 191, 22, 61, 33, 43, 156, 35, 51, 100, 22, 224, 59, 61, 188, 21, 193, 143, 88, 60, 123, 41, 119, 14, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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