Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec44ca504a389418806fb5b5f1940e83002d90577813fa2f05006892a5438333

Tx prefix hash: 76b79138fe2fa2bc4ae448b1f561585c09050ee889516a2d586938321ec75fe2
Tx public key: d6b1f41d9c463e81b1a9c87437d8c4c0ff3ab3408ebbc30ed0b430d772f615a8
Timestamp: 1762007618 Timestamp [UCT]: 2025-11-01 14:33:38 Age [y:d:h:m:s]: 00:014:02:49:52
Block: 1402724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10077 RingCT/type: yes/0
Extra: 01d6b1f41d9c463e81b1a9c87437d8c4c0ff3ab3408ebbc30ed0b430d772f615a802110000000fdf5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 864fcc4e6b91cf0f2e27a162a210a93a96cbd327677de90d880351555e124ae3 0.600000000000 1891043 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": 1402734, "vin": [ { "gen": { "height": 1402724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "864fcc4e6b91cf0f2e27a162a210a93a96cbd327677de90d880351555e124ae3" } } ], "extra": [ 1, 214, 177, 244, 29, 156, 70, 62, 129, 177, 169, 200, 116, 55, 216, 196, 192, 255, 58, 179, 64, 142, 187, 195, 14, 208, 180, 48, 215, 114, 246, 21, 168, 2, 17, 0, 0, 0, 15, 223, 90, 36, 122, 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