Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c431ac5e3c1ff4addf9cd921ad7133e1fd6bad2262e94e8f3369dc1791709137

Tx prefix hash: f5bf896a02f16f7296291cc9135358bdb621566d05cbad4e8e4dbd5f5f210670
Tx public key: 6ffe0d03b86d2722a057a66082c7aa923bb13b9ccb7e738394dc414286acefe6
Timestamp: 1731971947 Timestamp [UCT]: 2024-11-18 23:19:07 Age [y:d:h:m:s]: 01:003:01:07:34
Block: 1156716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260591 RingCT/type: yes/0
Extra: 016ffe0d03b86d2722a057a66082c7aa923bb13b9ccb7e738394dc414286acefe6021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f21732e1b7299e6b818c8c782da0581569a9dbc833990ae47d6304136aaf2a0e 0.600000000000 1642339 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": 1156726, "vin": [ { "gen": { "height": 1156716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f21732e1b7299e6b818c8c782da0581569a9dbc833990ae47d6304136aaf2a0e" } } ], "extra": [ 1, 111, 254, 13, 3, 184, 109, 39, 34, 160, 87, 166, 96, 130, 199, 170, 146, 59, 177, 59, 156, 203, 126, 115, 131, 148, 220, 65, 66, 134, 172, 239, 230, 2, 17, 0, 0, 0, 3, 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