Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6659c58f7521bf266ca3143f5f20c0e3d9f2d54d9b7068796efb90ff37d81d06

Tx prefix hash: 9343e9d38b64533d3a01f3def480e4713f198d1e25237a5549f4ecd20fd6c739
Tx public key: 278d45419324db5338d95ba24d23f69477bcdaa3af55ecd85a011207754b9ea8
Timestamp: 1677941748 Timestamp [UCT]: 2023-03-04 14:55:48 Age [y:d:h:m:s]: 01:359:02:07:15
Block: 709760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517311 RingCT/type: yes/0
Extra: 01278d45419324db5338d95ba24d23f69477bcdaa3af55ecd85a011207754b9ea80211000000015029cbac000000000000000000

1 output(s) for total of 2.730677322000 dcy

stealth address amount amount idx
00: 59e6169ed43a6d0de0e040ae7ed8b00a54746fd6a96cf42c3c356fa924abbdf9 2.730677322000 1153775 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": 709770, "vin": [ { "gen": { "height": 709760 } } ], "vout": [ { "amount": 2730677322, "target": { "key": "59e6169ed43a6d0de0e040ae7ed8b00a54746fd6a96cf42c3c356fa924abbdf9" } } ], "extra": [ 1, 39, 141, 69, 65, 147, 36, 219, 83, 56, 217, 91, 162, 77, 35, 246, 148, 119, 188, 218, 163, 175, 85, 236, 216, 90, 1, 18, 7, 117, 75, 158, 168, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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