Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d43303c0ff5fb53b9c314a3411897c3605cf4424867da21c50ec0396e047f67

Tx prefix hash: 7c344202ccc7edb3fbe5c5b99237774e5d02f91f5cbd1d307d6a4945fee85fc3
Tx public key: 466d7e35100a20da6a8116482f8116f58612c9dd1bdf421c2e8cd08c49b6c3a3
Timestamp: 1728660737 Timestamp [UCT]: 2024-10-11 15:32:17 Age [y:d:h:m:s]: 00:249:10:58:56
Block: 1129355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178001 RingCT/type: yes/0
Extra: 01466d7e35100a20da6a8116482f8116f58612c9dd1bdf421c2e8cd08c49b6c3a3021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eada517c3520306cf6bfd22d5d911752b79429cf744fcdd20c9648a6fc2cee9d 0.600000000000 1612180 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": 1129365, "vin": [ { "gen": { "height": 1129355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eada517c3520306cf6bfd22d5d911752b79429cf744fcdd20c9648a6fc2cee9d" } } ], "extra": [ 1, 70, 109, 126, 53, 16, 10, 32, 218, 106, 129, 22, 72, 47, 129, 22, 245, 134, 18, 201, 221, 27, 223, 66, 28, 46, 140, 208, 140, 73, 182, 195, 163, 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