Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dec7604acd6369f17128fd9c548733559f6cdcc5bb5eb2edee920e25e30e4e0

Tx prefix hash: a3ca7f59d20f27caf7b16d740a0afa15677ac669b6ee13c2c9bd5df608702825
Tx public key: 7ab126ab0829a4f16c1d7dd15a9f3dcb8097d48c9acacb017359dc489331b415
Timestamp: 1707987615 Timestamp [UCT]: 2024-02-15 09:00:15 Age [y:d:h:m:s]: 01:293:06:25:42
Block: 957965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468406 RingCT/type: yes/0
Extra: 017ab126ab0829a4f16c1d7dd15a9f3dcb8097d48c9acacb017359dc489331b41502110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24ad7f8bc218e8a9caf4aed8cb018387c7932eb8ae2afcea574434055e1c3975 0.600000000000 1417316 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": 957975, "vin": [ { "gen": { "height": 957965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24ad7f8bc218e8a9caf4aed8cb018387c7932eb8ae2afcea574434055e1c3975" } } ], "extra": [ 1, 122, 177, 38, 171, 8, 41, 164, 241, 108, 29, 125, 209, 90, 159, 61, 203, 128, 151, 212, 140, 154, 202, 203, 1, 115, 89, 220, 72, 147, 49, 180, 21, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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