Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 618abcf4fb3d3a53d9a81d15044afe23fc3e04ba572447585cc0e3648fd181fe

Tx prefix hash: 3d0a790474e965d66bf285b5c5efc8e63757a917afc12fa8b47f80ccc88f0cfd
Tx public key: d590debd3d9e9bd427bbb2fddb1665717448dfe599ba68950b82c1c76a6e4336
Timestamp: 1742044096 Timestamp [UCT]: 2025-03-15 13:08:16 Age [y:d:h:m:s]: 00:250:06:14:14
Block: 1239853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176588 RingCT/type: yes/0
Extra: 01d590debd3d9e9bd427bbb2fddb1665717448dfe599ba68950b82c1c76a6e43360211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44f440aa303dc843079ad502f2fbde654431ef57df8cccd5bd99a1dbab3ba093 0.600000000000 1726818 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": 1239863, "vin": [ { "gen": { "height": 1239853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44f440aa303dc843079ad502f2fbde654431ef57df8cccd5bd99a1dbab3ba093" } } ], "extra": [ 1, 213, 144, 222, 189, 61, 158, 155, 212, 39, 187, 178, 253, 219, 22, 101, 113, 116, 72, 223, 229, 153, 186, 104, 149, 11, 130, 193, 199, 106, 110, 67, 54, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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