Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 652b7490306d8c76dd6921039a52b451cf86affd7115791e07910e7bd099b845

Tx prefix hash: c0576415fd0a6c4e6544230575b1669436fd806a7325e6f5a96ddfd46d1a0c5b
Tx public key: 5ef06dbc8fb8d0dc53dba6204be3fa9e390bc4ab891c8684ffd8b6fb9fe4f248
Timestamp: 1732120202 Timestamp [UCT]: 2024-11-20 16:30:02 Age [y:d:h:m:s]: 00:137:02:31:41
Block: 1157943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97795 RingCT/type: yes/0
Extra: 015ef06dbc8fb8d0dc53dba6204be3fa9e390bc4ab891c8684ffd8b6fb9fe4f2480211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c4806e1ef0cdaa3cea55e5cf0ace199354e8facc193423f7f63166d0ca5a330 0.600000000000 1643566 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": 1157953, "vin": [ { "gen": { "height": 1157943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c4806e1ef0cdaa3cea55e5cf0ace199354e8facc193423f7f63166d0ca5a330" } } ], "extra": [ 1, 94, 240, 109, 188, 143, 184, 208, 220, 83, 219, 166, 32, 75, 227, 250, 158, 57, 11, 196, 171, 137, 28, 134, 132, 255, 216, 182, 251, 159, 228, 242, 72, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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