Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99d2bfc860f8c8bd3130801597d30cdcc9abf87b83a9868c3741b4d55b7df275

Tx prefix hash: ff33726fc09bb081fde3e7b83664c07dbfcdb263166e829fa54c1f0620770e05
Tx public key: d4c4f26286f6d4ef0d595d5616e0a56c18e97f600ecf7669498e2e5930cc95d4
Timestamp: 1646057092 Timestamp [UCT]: 2022-02-28 14:04:52 Age [y:d:h:m:s]: 03:246:16:17:59
Block: 448378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 954102 RingCT/type: yes/0
Extra: 01d4c4f26286f6d4ef0d595d5616e0a56c18e97f600ecf7669498e2e5930cc95d402110000000ba272b9cb000000000000000000

1 output(s) for total of 20.060319077000 dcy

stealth address amount amount idx
00: e5e38abe6afe0c74bf2cd071910cd930a10d181cf9a0324fbe96f44a829c15b9 20.060319077000 862737 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": 448388, "vin": [ { "gen": { "height": 448378 } } ], "vout": [ { "amount": 20060319077, "target": { "key": "e5e38abe6afe0c74bf2cd071910cd930a10d181cf9a0324fbe96f44a829c15b9" } } ], "extra": [ 1, 212, 196, 242, 98, 134, 246, 212, 239, 13, 89, 93, 86, 22, 224, 165, 108, 24, 233, 127, 96, 14, 207, 118, 105, 73, 142, 46, 89, 48, 204, 149, 212, 2, 17, 0, 0, 0, 11, 162, 114, 185, 203, 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