Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b41fbcf35f585d321cc03f70966c57da2ecb2ab8e342769e3496972776f0d991

Tx prefix hash: 14643053b4cba260f99cb78bef27a8d161b6583d93435a0f0df1737bd0b8766a
Tx public key: 81b8c4ad512ff6d2726110e9a23b7ddb9393fcc914d1f7e9d2868d113a009002
Timestamp: 1731203712 Timestamp [UCT]: 2024-11-10 01:55:12 Age [y:d:h:m:s]: 00:195:08:12:18
Block: 1150362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139465 RingCT/type: yes/0
Extra: 0181b8c4ad512ff6d2726110e9a23b7ddb9393fcc914d1f7e9d2868d113a0090020211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e74bb1876d109aacb0ba2357530b110835b043e4c278f4840b7f4a3045ab0bbd 0.600000000000 1635651 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": 1150372, "vin": [ { "gen": { "height": 1150362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e74bb1876d109aacb0ba2357530b110835b043e4c278f4840b7f4a3045ab0bbd" } } ], "extra": [ 1, 129, 184, 196, 173, 81, 47, 246, 210, 114, 97, 16, 233, 162, 59, 125, 219, 147, 147, 252, 201, 20, 209, 247, 233, 210, 134, 141, 17, 58, 0, 144, 2, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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