Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc5a8bc5e0481c7e10c79f99a38b0ec2b928290489ed4b4672375c50f3b31384

Tx prefix hash: b6dff483ffd1e2c2e95eb4f87f0569a22173b3d0abb679a2557e1513a9da4c20
Tx public key: 1e16061a2dd8a4a1eadfce2e85faaf6ddb038607aa4185616b2ec88134546bb8
Timestamp: 1725149918 Timestamp [UCT]: 2024-09-01 00:18:38 Age [y:d:h:m:s]: 01:060:02:03:16
Block: 1100246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301381 RingCT/type: yes/0
Extra: 011e16061a2dd8a4a1eadfce2e85faaf6ddb038607aa4185616b2ec88134546bb802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5795e9491d11a780dd9ed9601e8ddcc8da36c7089e8e4cf0bb77ac69ac5babd2 0.600000000000 1576221 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": 1100256, "vin": [ { "gen": { "height": 1100246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5795e9491d11a780dd9ed9601e8ddcc8da36c7089e8e4cf0bb77ac69ac5babd2" } } ], "extra": [ 1, 30, 22, 6, 26, 45, 216, 164, 161, 234, 223, 206, 46, 133, 250, 175, 109, 219, 3, 134, 7, 170, 65, 133, 97, 107, 46, 200, 129, 52, 84, 107, 184, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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