Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b358d8519405acb776636083c0f5c53a7b7952dcff45318b748264d387626177

Tx prefix hash: 0b0eb82d0cabdd3c341ce95b97d51a7d1f37cfb219d2e27e9f81101d033768f6
Tx public key: 0c3e3e48c756b0124fca925c717e4a96ad2ca0ca10f6648748b6812ba7efeb7c
Timestamp: 1703607678 Timestamp [UCT]: 2023-12-26 16:21:18 Age [y:d:h:m:s]: 01:317:22:13:17
Block: 921654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486056 RingCT/type: yes/0
Extra: 010c3e3e48c756b0124fca925c717e4a96ad2ca0ca10f6648748b6812ba7efeb7c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68187101cd07c7347f80106b3b52e1f8787b3a9ee6b98b5015e52db26db3a924 0.600000000000 1379344 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": 921664, "vin": [ { "gen": { "height": 921654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68187101cd07c7347f80106b3b52e1f8787b3a9ee6b98b5015e52db26db3a924" } } ], "extra": [ 1, 12, 62, 62, 72, 199, 86, 176, 18, 79, 202, 146, 92, 113, 126, 74, 150, 173, 44, 160, 202, 16, 246, 100, 135, 72, 182, 129, 43, 167, 239, 235, 124, 2, 17, 0, 0, 0, 2, 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