Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a12083e0387f65b2e075c4aec6a8e6a98c4d326c2bdeeaecfeaadf34a702fc70

Tx prefix hash: df944c63c212b080682b88757921ee359535554ad07ea8df0c55bc33c7f20c69
Tx public key: a930f0d571cceef6a57e9767eb2f6ea634fb314431a1e96ffe7794daf23d46cc
Timestamp: 1581112711 Timestamp [UCT]: 2020-02-07 21:58:31 Age [y:d:h:m:s]: 05:004:01:55:35
Block: 60782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155061 RingCT/type: yes/0
Extra: 01a930f0d571cceef6a57e9767eb2f6ea634fb314431a1e96ffe7794daf23d46cc0211000000644ac5aa02000000000000000000

1 output(s) for total of 386.015567346000 dcy

stealth address amount amount idx
00: a67e23502ba807a823a61172bc7994ce8a945083fbadf566feeab8c80f19c740 386.015567346000 111945 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": 60792, "vin": [ { "gen": { "height": 60782 } } ], "vout": [ { "amount": 386015567346, "target": { "key": "a67e23502ba807a823a61172bc7994ce8a945083fbadf566feeab8c80f19c740" } } ], "extra": [ 1, 169, 48, 240, 213, 113, 204, 238, 246, 165, 126, 151, 103, 235, 47, 110, 166, 52, 251, 49, 68, 49, 161, 233, 111, 254, 119, 148, 218, 242, 61, 70, 204, 2, 17, 0, 0, 0, 100, 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