Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12041ee000b060fdc3758b569790d66358538230853de0e2899bb11c4b13fe35

Tx prefix hash: 8cfb3221c8cdfcee3aca5850e4ad1e0bf76aa593d3d029015f19f62e97e011d0
Tx public key: e56e996cced5fad5e7eaec5cf2beb3ad9550d68bb7face5c3b42f4a0bc9fdc10
Timestamp: 1716821013 Timestamp [UCT]: 2024-05-27 14:43:33 Age [y:d:h:m:s]: 00:296:08:43:37
Block: 1031225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211809 RingCT/type: yes/0
Extra: 01e56e996cced5fad5e7eaec5cf2beb3ad9550d68bb7face5c3b42f4a0bc9fdc1002110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57ea79d2e8dadd9953bb7d7f62de6f157cba41e7669824bdc9fc825a9da43795 0.600000000000 1499618 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": 1031235, "vin": [ { "gen": { "height": 1031225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57ea79d2e8dadd9953bb7d7f62de6f157cba41e7669824bdc9fc825a9da43795" } } ], "extra": [ 1, 229, 110, 153, 108, 206, 213, 250, 213, 231, 234, 236, 92, 242, 190, 179, 173, 149, 80, 214, 139, 183, 250, 206, 92, 59, 66, 244, 160, 188, 159, 220, 16, 2, 17, 0, 0, 0, 5, 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