Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 106a883c6b76240183e36bda3c9d64ac9b15006ff2333c27f4e5454a329d634c

Tx prefix hash: 5ca5cc7b31ba55c0ef16c962f628482b6bd75147fd1d10485cd8f80799caa4b2
Tx public key: 04dd837a2340edd5448cfa958740e1a1f63b84f467a9b8bd4ece24aa232eba82
Timestamp: 1735758059 Timestamp [UCT]: 2025-01-01 19:00:59 Age [y:d:h:m:s]: 00:168:22:44:00
Block: 1188062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120452 RingCT/type: yes/0
Extra: 0104dd837a2340edd5448cfa958740e1a1f63b84f467a9b8bd4ece24aa232eba82021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0571768081e81c96e4ec2bef3fdbb7fb0261db7f8b3b4d1dc1814736b3a26d3 0.600000000000 1674561 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": 1188072, "vin": [ { "gen": { "height": 1188062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0571768081e81c96e4ec2bef3fdbb7fb0261db7f8b3b4d1dc1814736b3a26d3" } } ], "extra": [ 1, 4, 221, 131, 122, 35, 64, 237, 213, 68, 140, 250, 149, 135, 64, 225, 161, 246, 59, 132, 244, 103, 169, 184, 189, 78, 206, 36, 170, 35, 46, 186, 130, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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