Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 246568a262ad8be494673ff6fba6435ff4ff0e6e6c306aaaa8b62051a62161a1

Tx prefix hash: 5388f0aa2874add86fdda168dfc402fc97afe5829f766b358368f6a4bf450321
Tx public key: aa99cf9508f44f02603d275c70602b5c27b2a8ea883670e9b49dc770a054f1d4
Timestamp: 1744540345 Timestamp [UCT]: 2025-04-13 10:32:25 Age [y:d:h:m:s]: 00:221:03:57:44
Block: 1260503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155785 RingCT/type: yes/0
Extra: 01aa99cf9508f44f02603d275c70602b5c27b2a8ea883670e9b49dc770a054f1d40211000000116c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fe7e9680f9d022e6dc7a15a8624e1e5116f2bbeae0c6d56d0f8ac1b2c65bb41 0.600000000000 1747662 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": 1260513, "vin": [ { "gen": { "height": 1260503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fe7e9680f9d022e6dc7a15a8624e1e5116f2bbeae0c6d56d0f8ac1b2c65bb41" } } ], "extra": [ 1, 170, 153, 207, 149, 8, 244, 79, 2, 96, 61, 39, 92, 112, 96, 43, 92, 39, 178, 168, 234, 136, 54, 112, 233, 180, 157, 199, 112, 160, 84, 241, 212, 2, 17, 0, 0, 0, 17, 108, 152, 170, 61, 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