Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 025107c57ded35d4f3fd618d517f313f9a462de95f4d2b5bc8baec7350c2ebdc

Tx prefix hash: 6a4eaa142afd3521bf4b508ecfc0af37a77f5a43b3db750b4ad47975bef99a87
Tx public key: f720c9bd8f0fd4d56ee93149e9dccb4b6a467113821bbf79ff83cdac931aabb8
Timestamp: 1731976066 Timestamp [UCT]: 2024-11-19 00:27:46 Age [y:d:h:m:s]: 00:207:04:46:57
Block: 1156754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147864 RingCT/type: yes/0
Extra: 01f720c9bd8f0fd4d56ee93149e9dccb4b6a467113821bbf79ff83cdac931aabb8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13dedf309edf1e645b7d1ab91009c4cf8bc14ac3f31ded65426f4379ad050505 0.600000000000 1642377 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": 1156764, "vin": [ { "gen": { "height": 1156754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13dedf309edf1e645b7d1ab91009c4cf8bc14ac3f31ded65426f4379ad050505" } } ], "extra": [ 1, 247, 32, 201, 189, 143, 15, 212, 213, 110, 233, 49, 73, 233, 220, 203, 75, 106, 70, 113, 19, 130, 27, 191, 121, 255, 131, 205, 172, 147, 26, 171, 184, 2, 17, 0, 0, 0, 1, 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