Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 579188399557018b3b7aa21851039f74b8b8d13d00cbc6e06267ad6f222afed6

Tx prefix hash: a1e4f99d4c2a69b09a02820f314e5d8ac4fe0d9d706f55d7e97f3b707f56b9c7
Tx public key: df062e087ead3d8a34fd93d07ee27f934fe4c79f430fa31da5d51153962e1dc9
Timestamp: 1716963876 Timestamp [UCT]: 2024-05-29 06:24:36 Age [y:d:h:m:s]: 00:352:07:55:25
Block: 1032393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251831 RingCT/type: yes/0
Extra: 01df062e087ead3d8a34fd93d07ee27f934fe4c79f430fa31da5d51153962e1dc90211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c68a472947ce1da1a2103c987adaa242606ce1efa3b5c25c4da80de84077166e 0.600000000000 1500846 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": 1032403, "vin": [ { "gen": { "height": 1032393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c68a472947ce1da1a2103c987adaa242606ce1efa3b5c25c4da80de84077166e" } } ], "extra": [ 1, 223, 6, 46, 8, 126, 173, 61, 138, 52, 253, 147, 208, 126, 226, 127, 147, 79, 228, 199, 159, 67, 15, 163, 29, 165, 213, 17, 83, 150, 46, 29, 201, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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