Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c89481d6a798edff1ea9269b3d13ff0cbd01f105daa32ee3faf0f54612f20ae

Tx prefix hash: e449f5edc94216745955a643ab69849261b9df1854b064b9dd9fa7b3c14edad4
Tx public key: 0a3bb5b29773cf7ffd79c17cceb1737f513f3b5b771e6c7d3828280d9a9f940f
Timestamp: 1719247621 Timestamp [UCT]: 2024-06-24 16:47:01 Age [y:d:h:m:s]: 01:148:15:14:28
Block: 1051300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364805 RingCT/type: yes/0
Extra: 010a3bb5b29773cf7ffd79c17cceb1737f513f3b5b771e6c7d3828280d9a9f940f0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 415bfa86a4882611277d9770189cf5a6b636a446368f0bbb60959a028210de6a 0.600000000000 1521609 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": 1051310, "vin": [ { "gen": { "height": 1051300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "415bfa86a4882611277d9770189cf5a6b636a446368f0bbb60959a028210de6a" } } ], "extra": [ 1, 10, 59, 181, 178, 151, 115, 207, 127, 253, 121, 193, 124, 206, 177, 115, 127, 81, 63, 59, 91, 119, 30, 108, 125, 56, 40, 40, 13, 154, 159, 148, 15, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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