Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81f423c88087195f32b91f4e9cf0b4f73d50f9d9933a0b4d806c275596426170

Tx prefix hash: 4e1332304dc33a6affa21bdb4a658a8ee6abfd7d609dd0c01dd2c2fcd26feddf
Tx public key: 77872a2d28888e09feba9888d89b8d250596d58cc43a8001072c531ab2c1ffa7
Timestamp: 1732121504 Timestamp [UCT]: 2024-11-20 16:51:44 Age [y:d:h:m:s]: 00:136:03:46:37
Block: 1157950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97130 RingCT/type: yes/0
Extra: 0177872a2d28888e09feba9888d89b8d250596d58cc43a8001072c531ab2c1ffa70211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8630d10561a1a4fe60cadf893b37b25d76182c610d03eeb9f40eee4a4a49cbc3 0.600000000000 1643573 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": 1157960, "vin": [ { "gen": { "height": 1157950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8630d10561a1a4fe60cadf893b37b25d76182c610d03eeb9f40eee4a4a49cbc3" } } ], "extra": [ 1, 119, 135, 42, 45, 40, 136, 142, 9, 254, 186, 152, 136, 216, 155, 141, 37, 5, 150, 213, 140, 196, 58, 128, 1, 7, 44, 83, 26, 178, 193, 255, 167, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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