Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa97b7b414b9f0f90972a6ed62df46c02ad821d0539cc98511d31caba887187c

Tx prefix hash: 19ff06d8b6783bb4d35e7904ba3d860e81011f0bd5e13ed566e218bf73af6d34
Tx public key: 5422d3e818ea6f17cdff6e7368d999e39a120c888ad75b86681f0fe75ffc35c6
Timestamp: 1727825851 Timestamp [UCT]: 2024-10-01 23:37:31 Age [y:d:h:m:s]: 00:225:07:08:39
Block: 1122442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160847 RingCT/type: yes/0
Extra: 015422d3e818ea6f17cdff6e7368d999e39a120c888ad75b86681f0fe75ffc35c6021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b8d232c4158b1a7664ac812b1f05357d3ee5b2762239a0384fa28b9076bcc5e 0.600000000000 1604879 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": 1122452, "vin": [ { "gen": { "height": 1122442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b8d232c4158b1a7664ac812b1f05357d3ee5b2762239a0384fa28b9076bcc5e" } } ], "extra": [ 1, 84, 34, 211, 232, 24, 234, 111, 23, 205, 255, 110, 115, 104, 217, 153, 227, 154, 18, 12, 136, 138, 215, 91, 134, 104, 31, 15, 231, 95, 252, 53, 198, 2, 17, 0, 0, 0, 4, 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