Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50c86c76d36dd1fc48adedeb55ec35c99427ece3cb3586086a411a1392f8a9f2

Tx prefix hash: 1af5288356918bb4a696dbd229b3f5ec517d1d4063af6bb4d7e1bb28c0b22ed4
Tx public key: 0c93dc671ae18bf0eca455abaa8edc08781b0da34c7b1b6cf9111bedb2975c03
Timestamp: 1634780812 Timestamp [UCT]: 2021-10-21 01:46:52 Age [y:d:h:m:s]: 03:069:11:07:26
Block: 357138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 827880 RingCT/type: yes/0
Extra: 010c93dc671ae18bf0eca455abaa8edc08781b0da34c7b1b6cf9111bedb2975c03021100000006a272b9cb000000000000000000

1 output(s) for total of 40.239628641000 dcy

stealth address amount amount idx
00: 4bc04b0f740e8fd44c00c0177bd51925403b3cd124ae0fa92f85fa80ebc4dc4b 40.239628641000 728366 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": 357148, "vin": [ { "gen": { "height": 357138 } } ], "vout": [ { "amount": 40239628641, "target": { "key": "4bc04b0f740e8fd44c00c0177bd51925403b3cd124ae0fa92f85fa80ebc4dc4b" } } ], "extra": [ 1, 12, 147, 220, 103, 26, 225, 139, 240, 236, 164, 85, 171, 170, 142, 220, 8, 120, 27, 13, 163, 76, 123, 27, 108, 249, 17, 27, 237, 178, 151, 92, 3, 2, 17, 0, 0, 0, 6, 162, 114, 185, 203, 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