Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6203de9c4dfd63859adc4f4bdfa8aca698bddbae1979c55fe4c337e6ab0daa4c

Tx prefix hash: 61e94e2930901883a46a3b54442c3bf7279d4994b2ac502343ee52a3b3d446c5
Tx public key: f4d79a4bf4048c46c8c830bbe2f5438bd6bdebfa577c0a48e942bdf593b2dd9b
Timestamp: 1713823172 Timestamp [UCT]: 2024-04-22 21:59:32 Age [y:d:h:m:s]: 00:306:16:48:16
Block: 1006347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219213 RingCT/type: yes/0
Extra: 01f4d79a4bf4048c46c8c830bbe2f5438bd6bdebfa577c0a48e942bdf593b2dd9b02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccc4626752567952cb8d8f9666c60f1dab3ee25f48010c005a4c51ac098d3455 0.600000000000 1467357 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": 1006357, "vin": [ { "gen": { "height": 1006347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccc4626752567952cb8d8f9666c60f1dab3ee25f48010c005a4c51ac098d3455" } } ], "extra": [ 1, 244, 215, 154, 75, 244, 4, 140, 70, 200, 200, 48, 187, 226, 245, 67, 139, 214, 189, 235, 250, 87, 124, 10, 72, 233, 66, 189, 245, 147, 178, 221, 155, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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