Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cb47ff3853fe80e320fa9607b5a9bee8a3853cceedc3a8e0977468952d0e25f

Tx prefix hash: f5bddc017d674683b8ec5ca7782d36746551c7e50105dae530f444a8c60a9585
Tx public key: 8b83e8a9a0c2fd8b9d7c06b73341a3a6829cbe6cbe27348d21c0d72f17ce7f3c
Timestamp: 1675626628 Timestamp [UCT]: 2023-02-05 19:50:28 Age [y:d:h:m:s]: 01:300:22:32:53
Block: 690561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476026 RingCT/type: yes/0
Extra: 018b83e8a9a0c2fd8b9d7c06b73341a3a6829cbe6cbe27348d21c0d72f17ce7f3c021100000002e7ace25d000000000000000000

1 output(s) for total of 3.161437996000 dcy

stealth address amount amount idx
00: 3851d6812d09e52075751e04c86490f059e4fa076d578448150992a63925d284 3.161437996000 1133291 of 0

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": 690571, "vin": [ { "gen": { "height": 690561 } } ], "vout": [ { "amount": 3161437996, "target": { "key": "3851d6812d09e52075751e04c86490f059e4fa076d578448150992a63925d284" } } ], "extra": [ 1, 139, 131, 232, 169, 160, 194, 253, 139, 157, 124, 6, 183, 51, 65, 163, 166, 130, 156, 190, 108, 190, 39, 52, 141, 33, 192, 215, 47, 23, 206, 127, 60, 2, 17, 0, 0, 0, 2, 231, 172, 226, 93, 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