Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a1cd270c2410665a662dcd71d05722d76ad86d2b79f212f4bff406bdb819ad3

Tx prefix hash: af93ee52f34e819c95845c0e764fdf9684a7cdad14c8e9a60b84ca2b4afd186a
Tx public key: 68bdf7a86234c770301538354a7c54c3b2f45cfdbaec1e0efa9bf13d1bd66545
Timestamp: 1747668106 Timestamp [UCT]: 2025-05-19 15:21:46 Age [y:d:h:m:s]: 00:185:03:54:08
Block: 1286397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130042 RingCT/type: yes/0
Extra: 0168bdf7a86234c770301538354a7c54c3b2f45cfdbaec1e0efa9bf13d1bd665450211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 536a918b29edcbe85f22e3d44b6caae3f42e96e87895708a57df6070f90392da 0.600000000000 1773862 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": 1286407, "vin": [ { "gen": { "height": 1286397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "536a918b29edcbe85f22e3d44b6caae3f42e96e87895708a57df6070f90392da" } } ], "extra": [ 1, 104, 189, 247, 168, 98, 52, 199, 112, 48, 21, 56, 53, 74, 124, 84, 195, 178, 244, 92, 253, 186, 236, 30, 14, 250, 155, 241, 61, 27, 214, 101, 69, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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