Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6320f39b82f5611f7066e2bf25a5c8fd17122f65ab9feaa6fc029eb4280d869

Tx prefix hash: b4c685f946ffd83d09d017f0c39a8b12df8ffe0bc5a9065840f445ae13cb3b8f
Tx public key: 4c6ffb06c93cb6609ce28c8ae56dc6f74eb1baee27cc427b513aae854cdc16c5
Timestamp: 1694889580 Timestamp [UCT]: 2023-09-16 18:39:40 Age [y:d:h:m:s]: 01:128:06:39:29
Block: 849566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352952 RingCT/type: yes/0
Extra: 014c6ffb06c93cb6609ce28c8ae56dc6f74eb1baee27cc427b513aae854cdc16c50211000000054b8f5122000000000000000000

1 output(s) for total of 0.939799539000 dcy

stealth address amount amount idx
00: 521fd98df80109fd90b92558a81bc16877f1b4c78d21d9f92e93acfb5079a8b3 0.939799539000 1303236 of 0

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": 849576, "vin": [ { "gen": { "height": 849566 } } ], "vout": [ { "amount": 939799539, "target": { "key": "521fd98df80109fd90b92558a81bc16877f1b4c78d21d9f92e93acfb5079a8b3" } } ], "extra": [ 1, 76, 111, 251, 6, 201, 60, 182, 96, 156, 226, 140, 138, 229, 109, 198, 247, 78, 177, 186, 238, 39, 204, 66, 123, 81, 58, 174, 133, 76, 220, 22, 197, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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