Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36a1dec6c25b82b7737cee0d650aec61e5117c6577f257c0607bf60c93559fcf

Tx prefix hash: 6a24b5ca7b262f162b434c5a8f7bb1bf2e02c3f854f6a14d319334db2b7a51db
Tx public key: efab7960176c64d9dc1da6b52879d0c9a3ca874a15eff6123102a8b1dc079737
Timestamp: 1732746957 Timestamp [UCT]: 2024-11-27 22:35:57 Age [y:d:h:m:s]: 00:107:17:17:27
Block: 1163127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76813 RingCT/type: yes/0
Extra: 01efab7960176c64d9dc1da6b52879d0c9a3ca874a15eff6123102a8b1dc0797370211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3660feeba3c4e64cc58287993d63a49756be70e965e8ed8e6ba5ac3468901063 0.600000000000 1648794 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": 1163137, "vin": [ { "gen": { "height": 1163127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3660feeba3c4e64cc58287993d63a49756be70e965e8ed8e6ba5ac3468901063" } } ], "extra": [ 1, 239, 171, 121, 96, 23, 108, 100, 217, 220, 29, 166, 181, 40, 121, 208, 201, 163, 202, 135, 74, 21, 239, 246, 18, 49, 2, 168, 177, 220, 7, 151, 55, 2, 17, 0, 0, 0, 1, 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