Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08fd8928aeaf3621efe07417e72d1d7fb773e3bd8e2b773a88333450baf9e2c1

Tx prefix hash: ec158e55a233c4e8f99f8099f63da68d84052a27fdc3bf02736ae8d031eb52a6
Tx public key: 60029e925474ec4378b8a586923d669af59df27854fe137a9673b8ad98fd19b1
Timestamp: 1695220725 Timestamp [UCT]: 2023-09-20 14:38:45 Age [y:d:h:m:s]: 01:250:02:43:57
Block: 852317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439868 RingCT/type: yes/0
Extra: 0160029e925474ec4378b8a586923d669af59df27854fe137a9673b8ad98fd19b1021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.920310074000 dcy

stealth address amount amount idx
00: b123153002032923d4660353927b4d3c9b3e7793f40e7b1bb76393c7250a64b3 0.920310074000 1306145 of 0

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": 852327, "vin": [ { "gen": { "height": 852317 } } ], "vout": [ { "amount": 920310074, "target": { "key": "b123153002032923d4660353927b4d3c9b3e7793f40e7b1bb76393c7250a64b3" } } ], "extra": [ 1, 96, 2, 158, 146, 84, 116, 236, 67, 120, 184, 165, 134, 146, 61, 102, 154, 245, 157, 242, 120, 84, 254, 19, 122, 150, 115, 184, 173, 152, 253, 25, 177, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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