Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b7f054862599c33115c3b661e5a0e7b787e99932e2696f5be2d31681a1ae287

Tx prefix hash: 1ddc2571d619024305692b6e77297364a2ca8b7e74da04dc35b8695f8b8cbb28
Tx public key: d8756a03d2fa26ee59c75dcd6394904fda8650c54f91d3aa471066fcdddc0903
Timestamp: 1745663758 Timestamp [UCT]: 2025-04-26 10:35:58 Age [y:d:h:m:s]: 00:209:03:33:12
Block: 1269813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147182 RingCT/type: yes/0
Extra: 01d8756a03d2fa26ee59c75dcd6394904fda8650c54f91d3aa471066fcdddc090302110000000cdbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df4741e96f398ca5f65c7e8a0b3bd268b0cbe404a56712a85e702d928648c49d 0.600000000000 1757052 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": 1269823, "vin": [ { "gen": { "height": 1269813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df4741e96f398ca5f65c7e8a0b3bd268b0cbe404a56712a85e702d928648c49d" } } ], "extra": [ 1, 216, 117, 106, 3, 210, 250, 38, 238, 89, 199, 93, 205, 99, 148, 144, 79, 218, 134, 80, 197, 79, 145, 211, 170, 71, 16, 102, 252, 221, 220, 9, 3, 2, 17, 0, 0, 0, 12, 219, 181, 113, 193, 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