Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e46dc866ff392a9b71e8472845ad0ef1bca7ffa6378d1cfc9c53f34ee499f18

Tx prefix hash: 8100e527a7d048939524d2c8633cf671de9a5ad4fa7ed6da18349563bb37a686
Tx public key: 1648385fd5a60b28a088c46df671eed7de61814dba512f70950f0466ff00ba7c
Timestamp: 1705785397 Timestamp [UCT]: 2024-01-20 21:16:37 Age [y:d:h:m:s]: 01:081:08:30:21
Block: 939675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319262 RingCT/type: yes/0
Extra: 011648385fd5a60b28a088c46df671eed7de61814dba512f70950f0466ff00ba7c02110000000c0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b21b29d71e132befec4ecebee21e4b7a1a8b1f181c26e234171e9a2522a2a6b5 0.600000000000 1397785 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": 939685, "vin": [ { "gen": { "height": 939675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b21b29d71e132befec4ecebee21e4b7a1a8b1f181c26e234171e9a2522a2a6b5" } } ], "extra": [ 1, 22, 72, 56, 95, 213, 166, 11, 40, 160, 136, 196, 109, 246, 113, 238, 215, 222, 97, 129, 77, 186, 81, 47, 112, 149, 15, 4, 102, 255, 0, 186, 124, 2, 17, 0, 0, 0, 12, 0, 17, 5, 91, 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