Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d4c6870cc50ab0ce2df8043638cbfdaed831c4fb44a16e9437f3145f07d31cd

Tx prefix hash: e75ef7b11830405ba2dc1975a2b68caf0fa57d3bf9708845011e652fb254e4f3
Tx public key: 516ecd24dd54966918dd323c2e0114acf16f9b13e59d82de190df1a8b6e24bd8
Timestamp: 1710976111 Timestamp [UCT]: 2024-03-20 23:08:31 Age [y:d:h:m:s]: 01:008:12:12:31
Block: 982763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267040 RingCT/type: yes/0
Extra: 01516ecd24dd54966918dd323c2e0114acf16f9b13e59d82de190df1a8b6e24bd802110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8be56edc1c112b40e33d0e6a6a9763be64f6068daf7faf67dbd8b48a95ff903b 0.600000000000 1442874 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": 982773, "vin": [ { "gen": { "height": 982763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8be56edc1c112b40e33d0e6a6a9763be64f6068daf7faf67dbd8b48a95ff903b" } } ], "extra": [ 1, 81, 110, 205, 36, 221, 84, 150, 105, 24, 221, 50, 60, 46, 1, 20, 172, 241, 111, 155, 19, 229, 157, 130, 222, 25, 13, 241, 168, 182, 226, 75, 216, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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