Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e4b4e1df0b9aa26086db64c8de3bff8bd1ddc303bc92a6e1bfc6009eddec22a

Tx prefix hash: 7eb52e0260d97b38e7fe7eb75f4cc60e63cbcdb28c06fa1e2b1184d6943d18d7
Tx public key: 5f975b91730f400cb1f104186906045836826d9a0bc2662f5564f39c9e9895df
Timestamp: 1727955084 Timestamp [UCT]: 2024-10-03 11:31:24 Age [y:d:h:m:s]: 00:183:15:08:38
Block: 1123508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131030 RingCT/type: yes/0
Extra: 015f975b91730f400cb1f104186906045836826d9a0bc2662f5564f39c9e9895df021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9f7d3e56357227601e62f452333aa3817784535895e5fbdf60e9cd17366f25f 0.600000000000 1606043 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": 1123518, "vin": [ { "gen": { "height": 1123508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9f7d3e56357227601e62f452333aa3817784535895e5fbdf60e9cd17366f25f" } } ], "extra": [ 1, 95, 151, 91, 145, 115, 15, 64, 12, 177, 241, 4, 24, 105, 6, 4, 88, 54, 130, 109, 154, 11, 194, 102, 47, 85, 100, 243, 156, 158, 152, 149, 223, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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