Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef8428614fe5943aa9387fcd8bf22009d671b78ab425a844f6326177e510e600

Tx prefix hash: 8ae74e99e0d285b167c45db590d729c95b46de178f3a0ae57e1143ddac4a4cf1
Tx public key: 37c7d1d54190f545e36d1d2974b5996280bd0b13ef01ef3f21ba139eb3acb60a
Timestamp: 1704292329 Timestamp [UCT]: 2024-01-03 14:32:09 Age [y:d:h:m:s]: 01:026:09:12:27
Block: 927346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279915 RingCT/type: yes/0
Extra: 0137c7d1d54190f545e36d1d2974b5996280bd0b13ef01ef3f21ba139eb3acb60a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 277f4b74b3767dfa15e7b9b55271f5d5bdc49e392e67816b1e7156ba59a36b7c 0.600000000000 1385182 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": 927356, "vin": [ { "gen": { "height": 927346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "277f4b74b3767dfa15e7b9b55271f5d5bdc49e392e67816b1e7156ba59a36b7c" } } ], "extra": [ 1, 55, 199, 209, 213, 65, 144, 245, 69, 227, 109, 29, 41, 116, 181, 153, 98, 128, 189, 11, 19, 239, 1, 239, 63, 33, 186, 19, 158, 179, 172, 182, 10, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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