Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c930798ff476ddf144ae527a67cab009dc58e5f4093e883101bf050bf83adb1

Tx prefix hash: 54995bff68dcdd985712a3a77ed11a5a54eb5a2de9f314aa4cfbe6a5ba301c21
Tx public key: 866ae47e9c083b67c887b449e515100705797e19de9b6dada3b34fd77ea076ab
Timestamp: 1711148111 Timestamp [UCT]: 2024-03-22 22:55:11 Age [y:d:h:m:s]: 00:360:03:28:38
Block: 984191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257483 RingCT/type: yes/0
Extra: 01866ae47e9c083b67c887b449e515100705797e19de9b6dada3b34fd77ea076ab0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d65e7b1285e4fea0f3bca4f3c8d04c2baa8360e571e130d95db26e4961b9336 0.600000000000 1444356 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": 984201, "vin": [ { "gen": { "height": 984191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d65e7b1285e4fea0f3bca4f3c8d04c2baa8360e571e130d95db26e4961b9336" } } ], "extra": [ 1, 134, 106, 228, 126, 156, 8, 59, 103, 200, 135, 180, 73, 229, 21, 16, 7, 5, 121, 126, 25, 222, 155, 109, 173, 163, 179, 79, 215, 126, 160, 118, 171, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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