Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44afa75d7c53b356bcbefbdb8826a22b7c9cdd8bf1bec1082d9536ddf888ce97

Tx prefix hash: 9b9df162f9d7e103b76f7fc0723bcb9e4df2d1e9615e6028b020f3dec9ac1d3b
Tx public key: d7de2339db0fa45cdd5b40042b7385d2baf62103cf6fdd021ae37f8a89cee9db
Timestamp: 1746567866 Timestamp [UCT]: 2025-05-06 21:44:26 Age [y:d:h:m:s]: 00:198:00:35:33
Block: 1277284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139245 RingCT/type: yes/0
Extra: 01d7de2339db0fa45cdd5b40042b7385d2baf62103cf6fdd021ae37f8a89cee9db021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95f58cec8ad94f155481f7a63750a5e0f3d7008a0918520218f951a592a33899 0.600000000000 1764639 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": 1277294, "vin": [ { "gen": { "height": 1277284 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95f58cec8ad94f155481f7a63750a5e0f3d7008a0918520218f951a592a33899" } } ], "extra": [ 1, 215, 222, 35, 57, 219, 15, 164, 92, 221, 91, 64, 4, 43, 115, 133, 210, 186, 246, 33, 3, 207, 111, 221, 2, 26, 227, 127, 138, 137, 206, 233, 219, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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