Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f17b5115058dfeafada825039b3e095ee1eea5de4a617cd298f33fe5df9d1759

Tx prefix hash: 99a08aa0bec23dd7276dd7f12d2c4e1989648310d7eb32251382844c957ed05b
Tx public key: 91d83309cd8ba4e7e8a19a7551b760118661b96da3ecb59a4c1ba29d3d10d3f2
Timestamp: 1728704045 Timestamp [UCT]: 2024-10-12 03:34:05 Age [y:d:h:m:s]: 00:246:12:25:04
Block: 1129732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175894 RingCT/type: yes/0
Extra: 0191d83309cd8ba4e7e8a19a7551b760118661b96da3ecb59a4c1ba29d3d10d3f2021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec5ff5dda7776699b818c3b97cbbbb34556815c7c04128c6e2dfdfeb0a2e142b 0.600000000000 1612581 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": 1129742, "vin": [ { "gen": { "height": 1129732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec5ff5dda7776699b818c3b97cbbbb34556815c7c04128c6e2dfdfeb0a2e142b" } } ], "extra": [ 1, 145, 216, 51, 9, 205, 139, 164, 231, 232, 161, 154, 117, 81, 183, 96, 17, 134, 97, 185, 109, 163, 236, 181, 154, 76, 27, 162, 157, 61, 16, 211, 242, 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