Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d08079a943ce7d7f8419977b3d57ccc0aa9b7ced371d68288b470ce045ae2078

Tx prefix hash: f5a2bc36b2a92ca9125610d37faaa6f10b38b6ffcede84610ded5a7cd827d84b
Tx public key: e7c3f59ce0e064b2c8899b05ee0abd91014025661af4887a77ccc323fc19bc71
Timestamp: 1765527295 Timestamp [UCT]: 2025-12-12 08:14:55 Age [y:d:h:m:s]: 00:011:07:20:03
Block: 1431860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8090 RingCT/type: yes/0
Extra: 01e7c3f59ce0e064b2c8899b05ee0abd91014025661af4887a77ccc323fc19bc71021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e468009365d52758d4b096d32a25d84203a3aef5f43af68f0a3e357666ac89b2 0.600000000000 1920635 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": 1431870, "vin": [ { "gen": { "height": 1431860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e468009365d52758d4b096d32a25d84203a3aef5f43af68f0a3e357666ac89b2" } } ], "extra": [ 1, 231, 195, 245, 156, 224, 224, 100, 178, 200, 137, 155, 5, 238, 10, 189, 145, 1, 64, 37, 102, 26, 244, 136, 122, 119, 204, 195, 35, 252, 25, 188, 113, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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