Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 013ef2f0df6d22fd1b684aaf76ed1ce2e229d9bab60effd4b081cc39be12bfe0

Tx prefix hash: f195a7bb6dca80b16ae78a82b1fae515cfc27313b44d48405ebbb735c3593b93
Tx public key: 2adb9c1e4931063faed81ec7ef94fadd1346850e79c249bd9dbc78a35e530195
Timestamp: 1722131756 Timestamp [UCT]: 2024-07-28 01:55:56 Age [y:d:h:m:s]: 00:260:23:37:02
Block: 1075225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186440 RingCT/type: yes/0
Extra: 012adb9c1e4931063faed81ec7ef94fadd1346850e79c249bd9dbc78a35e53019502110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89dc5aadac51c6e0e6dea1e5b93ab1bf9ea8691eaf2a2d94bee85f920a7e786f 0.600000000000 1547748 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": 1075235, "vin": [ { "gen": { "height": 1075225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89dc5aadac51c6e0e6dea1e5b93ab1bf9ea8691eaf2a2d94bee85f920a7e786f" } } ], "extra": [ 1, 42, 219, 156, 30, 73, 49, 6, 63, 174, 216, 30, 199, 239, 148, 250, 221, 19, 70, 133, 14, 121, 194, 73, 189, 157, 188, 120, 163, 94, 83, 1, 149, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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