Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43172aee54aaf3292466c8936a414c8e230d826d1e6cbc78e4d212fd4b6c2032

Tx prefix hash: 0aa4bd736399f2209d45c572d64a2cf1e1a7d80d87710112df5694ae8cbabf1c
Tx public key: 01d0b7c9db4a9d32ded278043122f778beec3201795ce69d3e3c073bdde253a7
Timestamp: 1723858599 Timestamp [UCT]: 2024-08-17 01:36:39 Age [y:d:h:m:s]: 00:145:04:41:17
Block: 1089544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103866 RingCT/type: yes/0
Extra: 0101d0b7c9db4a9d32ded278043122f778beec3201795ce69d3e3c073bdde253a7021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a32294e2b38981d374a05266f8802f28a0915124e4b4fe26f4611b53a832437 0.600000000000 1564167 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": 1089554, "vin": [ { "gen": { "height": 1089544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a32294e2b38981d374a05266f8802f28a0915124e4b4fe26f4611b53a832437" } } ], "extra": [ 1, 1, 208, 183, 201, 219, 74, 157, 50, 222, 210, 120, 4, 49, 34, 247, 120, 190, 236, 50, 1, 121, 92, 230, 157, 62, 60, 7, 59, 221, 226, 83, 167, 2, 17, 0, 0, 0, 4, 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