Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0391b165142ed240b6ba2645f9250d5979df3cd7e10fa37ed070b0d88f239196

Tx prefix hash: 019ce6e5b5b837850f3efb204be4c559634311aebf5afa7dc46ddbba541dbfa1
Tx public key: 86ea3ef781b25b051555f4c825d4bc543aa48b77e5d909636e389e0723f78bff
Timestamp: 1700475820 Timestamp [UCT]: 2023-11-20 10:23:40 Age [y:d:h:m:s]: 01:212:09:09:37
Block: 895689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412885 RingCT/type: yes/0
Extra: 0186ea3ef781b25b051555f4c825d4bc543aa48b77e5d909636e389e0723f78bff02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.661013782000 dcy

stealth address amount amount idx
00: 87dda34f83e69b18237b1ed484564b306c85ffddcebbef952f3c8ec46993e7c2 0.661013782000 1351930 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": 895699, "vin": [ { "gen": { "height": 895689 } } ], "vout": [ { "amount": 661013782, "target": { "key": "87dda34f83e69b18237b1ed484564b306c85ffddcebbef952f3c8ec46993e7c2" } } ], "extra": [ 1, 134, 234, 62, 247, 129, 178, 91, 5, 21, 85, 244, 200, 37, 212, 188, 84, 58, 164, 139, 119, 229, 217, 9, 99, 110, 56, 158, 7, 35, 247, 139, 255, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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