Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8637876a39d580cf44812f7b63d6b3572e6dd041c967d5ddfac4b26f4751355

Tx prefix hash: c025437f63792cb671f5b3731985f8dccd1e934151b898dac20a88dd9f9ce036
Tx public key: e82ac2dc3ccf081f426ae9810f58fd26471258c57b9ef84b8af3f74dc3c0a1b7
Timestamp: 1726686922 Timestamp [UCT]: 2024-09-18 19:15:22 Age [y:d:h:m:s]: 00:211:13:57:18
Block: 1112994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151048 RingCT/type: yes/0
Extra: 01e82ac2dc3ccf081f426ae9810f58fd26471258c57b9ef84b8af3f74dc3c0a1b70211000000045a5c538d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44cce0ae13b4213116c80a7f064cc9ff56beb6b2e8afd85f8c86ac9e33fdb19d 0.600000000000 1592509 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": 1113004, "vin": [ { "gen": { "height": 1112994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44cce0ae13b4213116c80a7f064cc9ff56beb6b2e8afd85f8c86ac9e33fdb19d" } } ], "extra": [ 1, 232, 42, 194, 220, 60, 207, 8, 31, 66, 106, 233, 129, 15, 88, 253, 38, 71, 18, 88, 197, 123, 158, 248, 75, 138, 243, 247, 77, 195, 192, 161, 183, 2, 17, 0, 0, 0, 4, 90, 92, 83, 141, 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