Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25155962c47319a6bec58e83965c6b77b140b509da55b0c6a5d64d9cf5869520

Tx prefix hash: 979cbc352f594c28368677960a3225ed5912e62e14b5ee53b851520b232638f5
Tx public key: 243403f025b69fd2cff9068a2b320187c9df259b22ec1ca03e1a92315e519195
Timestamp: 1730074009 Timestamp [UCT]: 2024-10-28 00:06:49 Age [y:d:h:m:s]: 00:071:22:55:40
Block: 1141020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51455 RingCT/type: yes/0
Extra: 01243403f025b69fd2cff9068a2b320187c9df259b22ec1ca03e1a92315e519195021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4d1dbdccaee969d6575d3f8d4fee8434da70b591467bb726b2074584ecb66e6 0.600000000000 1624827 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": 1141030, "vin": [ { "gen": { "height": 1141020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4d1dbdccaee969d6575d3f8d4fee8434da70b591467bb726b2074584ecb66e6" } } ], "extra": [ 1, 36, 52, 3, 240, 37, 182, 159, 210, 207, 249, 6, 138, 43, 50, 1, 135, 201, 223, 37, 155, 34, 236, 28, 160, 62, 26, 146, 49, 94, 81, 145, 149, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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