Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 966dc9ae0f3b78903f4c9ceec78bbc7e882d9eb29fdba6180f4d8b6a11d2eeba

Tx prefix hash: 5fe9804ccfb8daf25fb04bfd4f8a08b85db6a6194367f27ca091257dbb148cce
Tx public key: 91edf0c90441fa4b19c9c4e4de203d4e01537f7cf405aa98250a1bfa93d5f800
Timestamp: 1634731593 Timestamp [UCT]: 2021-10-20 12:06:33 Age [y:d:h:m:s]: 03:041:02:22:19
Block: 356795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 807539 RingCT/type: yes/0
Extra: 0191edf0c90441fa4b19c9c4e4de203d4e01537f7cf405aa98250a1bfa93d5f8000211000000324a0f5013000000000000000000

1 output(s) for total of 40.345069319000 dcy

stealth address amount amount idx
00: 44aa5df788a311e4f8acb43717a34b58da442ff5daed5deb2579e17ddb7c4197 40.345069319000 727821 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": 356805, "vin": [ { "gen": { "height": 356795 } } ], "vout": [ { "amount": 40345069319, "target": { "key": "44aa5df788a311e4f8acb43717a34b58da442ff5daed5deb2579e17ddb7c4197" } } ], "extra": [ 1, 145, 237, 240, 201, 4, 65, 250, 75, 25, 201, 196, 228, 222, 32, 61, 78, 1, 83, 127, 124, 244, 5, 170, 152, 37, 10, 27, 250, 147, 213, 248, 0, 2, 17, 0, 0, 0, 50, 74, 15, 80, 19, 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