Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e85fc3745f1dc7f10563772ae47dcac06c66c8eba132a1c0b1d29cbf40986985

Tx prefix hash: fdd9a462ab392287363b1d0d6cd3aa4331f0d5caeacf08ea8470e33377696dad
Tx public key: 9dcfdaf7cc2de4161b8ba6a9e8d70ce9d0939d8df50d32e1ac4d267249930bde
Timestamp: 1725046170 Timestamp [UCT]: 2024-08-30 19:29:30 Age [y:d:h:m:s]: 00:295:22:55:36
Block: 1099390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211222 RingCT/type: yes/0
Extra: 019dcfdaf7cc2de4161b8ba6a9e8d70ce9d0939d8df50d32e1ac4d267249930bde021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cd9b58a9544b9d5861356a3934f1e67b4de8c60ebd9e34a49d047449ed9f583 0.600000000000 1575351 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": 1099400, "vin": [ { "gen": { "height": 1099390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cd9b58a9544b9d5861356a3934f1e67b4de8c60ebd9e34a49d047449ed9f583" } } ], "extra": [ 1, 157, 207, 218, 247, 204, 45, 228, 22, 27, 139, 166, 169, 232, 215, 12, 233, 208, 147, 157, 141, 245, 13, 50, 225, 172, 77, 38, 114, 73, 147, 11, 222, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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