Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 001dae3712de8f78fa7224538741d83b0b0217529ee519291d5a6e61efb59ace

Tx prefix hash: 7b28e602e5cff4218b823a1641086b8e552495d29cb23293b449fa6192e03e77
Tx public key: addc03b6f26d0f25f129d650ee0d473ae412a197e910d24bd379d96e8cb0d300
Timestamp: 1731665481 Timestamp [UCT]: 2024-11-15 10:11:21 Age [y:d:h:m:s]: 00:160:16:34:39
Block: 1154179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114683 RingCT/type: yes/0
Extra: 01addc03b6f26d0f25f129d650ee0d473ae412a197e910d24bd379d96e8cb0d300021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29b26bd8528b2f45a4990eb2ef4a1eda788b2cac62c37d3742a409e6d8153e2a 0.600000000000 1639790 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": 1154189, "vin": [ { "gen": { "height": 1154179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29b26bd8528b2f45a4990eb2ef4a1eda788b2cac62c37d3742a409e6d8153e2a" } } ], "extra": [ 1, 173, 220, 3, 182, 242, 109, 15, 37, 241, 41, 214, 80, 238, 13, 71, 58, 228, 18, 161, 151, 233, 16, 210, 75, 211, 121, 217, 110, 140, 176, 211, 0, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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