Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e9b7f01e1a5e26275f46a899fa0cfe4df8863cebd3846604f732474c0c6ff96

Tx prefix hash: 3491666c533fead9c540f76aaee9219bd4d13ee2bc1db3ac16b542218a7b1643
Tx public key: 4a8b2514dcbc2b8d107fb1a282ccb9daa71064d1b11db5b267e9f5a181db58ea
Timestamp: 1704877268 Timestamp [UCT]: 2024-01-10 09:01:08 Age [y:d:h:m:s]: 01:097:20:51:19
Block: 932168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331063 RingCT/type: yes/0
Extra: 014a8b2514dcbc2b8d107fb1a282ccb9daa71064d1b11db5b267e9f5a181db58ea02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27d93a93d14ce4c19821e8e4662667e879c1c716e19262003fe6f59713656cb3 0.600000000000 1390092 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": 932178, "vin": [ { "gen": { "height": 932168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27d93a93d14ce4c19821e8e4662667e879c1c716e19262003fe6f59713656cb3" } } ], "extra": [ 1, 74, 139, 37, 20, 220, 188, 43, 141, 16, 127, 177, 162, 130, 204, 185, 218, 167, 16, 100, 209, 177, 29, 181, 178, 103, 233, 245, 161, 129, 219, 88, 234, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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