Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01f2a7eb73b8cc1063bc14dc2654722eb5345b51d0e8ec9bb4339e29533d3b26

Tx prefix hash: b1e32074b5846d5898c0854df050dc1c2e7e692415699e38a53abba4f73d4f0a
Tx public key: 14fb69faaadffc2072f951ad9b9c02e540e203e8feb1f1cc48169aa47ef98199
Timestamp: 1709292378 Timestamp [UCT]: 2024-03-01 11:26:18 Age [y:d:h:m:s]: 00:329:13:39:05
Block: 968793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235872 RingCT/type: yes/0
Extra: 0114fb69faaadffc2072f951ad9b9c02e540e203e8feb1f1cc48169aa47ef9819902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8288c5a38e018a155a8affad33cee276dcde5d9bb828a218f533dd8d785bbbbf 0.600000000000 1428616 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": 968803, "vin": [ { "gen": { "height": 968793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8288c5a38e018a155a8affad33cee276dcde5d9bb828a218f533dd8d785bbbbf" } } ], "extra": [ 1, 20, 251, 105, 250, 170, 223, 252, 32, 114, 249, 81, 173, 155, 156, 2, 229, 64, 226, 3, 232, 254, 177, 241, 204, 72, 22, 154, 164, 126, 249, 129, 153, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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