Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6855c1a1c929b5adbc1a608f66074040fca2f81af0846ea55e54aaafcc190315

Tx prefix hash: c216b9920ffea3267fac181c95aa2cf4fbb0362aec4ab638a7c7c33536d29c77
Tx public key: b29772d6d5be082263842523b4f15fe28b6a8c95a12316f0bdefa2ad4fb12af9
Timestamp: 1705604914 Timestamp [UCT]: 2024-01-18 19:08:34 Age [y:d:h:m:s]: 01:072:14:58:25
Block: 938196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312991 RingCT/type: yes/0
Extra: 01b29772d6d5be082263842523b4f15fe28b6a8c95a12316f0bdefa2ad4fb12af902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ec6842756b4eaf6ad5dfe4b2a3bf7bd0be745af63d4938a70ecdef12699e09a 0.600000000000 1396266 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": 938206, "vin": [ { "gen": { "height": 938196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ec6842756b4eaf6ad5dfe4b2a3bf7bd0be745af63d4938a70ecdef12699e09a" } } ], "extra": [ 1, 178, 151, 114, 214, 213, 190, 8, 34, 99, 132, 37, 35, 180, 241, 95, 226, 139, 106, 140, 149, 161, 35, 22, 240, 189, 239, 162, 173, 79, 177, 42, 249, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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