Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3f02ec364bfd88e4d0d0c4039228f5a5d837970a5723522851e7bd025b24652

Tx prefix hash: 0a960e941e8c806986fb53f7039a66d922aac998a9ddab2a614ff3bedeaa1d18
Tx public key: 6f5095962ec89e7474e385cfa15a6e4cdcd31d3aeb988d0c15ecd5bef759dd2d
Timestamp: 1731058723 Timestamp [UCT]: 2024-11-08 09:38:43 Age [y:d:h:m:s]: 00:174:12:45:55
Block: 1149154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124577 RingCT/type: yes/0
Extra: 016f5095962ec89e7474e385cfa15a6e4cdcd31d3aeb988d0c15ecd5bef759dd2d0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2423f6b52ad31eeccda54ffb5cf3e3742295e2c8fc40e546abe280eae26fa882 0.600000000000 1634169 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": 1149164, "vin": [ { "gen": { "height": 1149154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2423f6b52ad31eeccda54ffb5cf3e3742295e2c8fc40e546abe280eae26fa882" } } ], "extra": [ 1, 111, 80, 149, 150, 46, 200, 158, 116, 116, 227, 133, 207, 161, 90, 110, 76, 220, 211, 29, 58, 235, 152, 141, 12, 21, 236, 213, 190, 247, 89, 221, 45, 2, 17, 0, 0, 0, 4, 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