Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1385da868c677b00791b262db384dc4036d0851c0447ddaaa46029ee9282e95

Tx prefix hash: d4eaff5d3deeff768f111f4d2f499ea845f1b60bdd2fc3b2fffb2b7955076926
Tx public key: 24d4473d5c4b1d3e7efe4221dd44f466a409eb0ebb09c69d32c4dcc3a501e702
Timestamp: 1727661664 Timestamp [UCT]: 2024-09-30 02:01:04 Age [y:d:h:m:s]: 00:114:08:54:06
Block: 1121072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81734 RingCT/type: yes/0
Extra: 0124d4473d5c4b1d3e7efe4221dd44f466a409eb0ebb09c69d32c4dcc3a501e70202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf4b776f2b185f9df804bd242cde4c69020312e12acb37442bbce2b749178a4c 0.600000000000 1603215 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": 1121082, "vin": [ { "gen": { "height": 1121072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf4b776f2b185f9df804bd242cde4c69020312e12acb37442bbce2b749178a4c" } } ], "extra": [ 1, 36, 212, 71, 61, 92, 75, 29, 62, 126, 254, 66, 33, 221, 68, 244, 102, 164, 9, 235, 14, 187, 9, 198, 157, 50, 196, 220, 195, 165, 1, 231, 2, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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