Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5755915b03b8b407662b91f7350ad23f010318fd8ad2d03000d16a9caee8752d

Tx prefix hash: 9c99eb6bff3f8b58f352ce677a1fb4c69e00b1e9943809113c9f71ced39c981a
Tx public key: 35257a13b526c4b721dc5e3ee574566bfcd9ed137a1176c63077932eff7f3d8f
Timestamp: 1707235884 Timestamp [UCT]: 2024-02-06 16:11:24 Age [y:d:h:m:s]: 01:000:11:36:42
Block: 951723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261371 RingCT/type: yes/0
Extra: 0135257a13b526c4b721dc5e3ee574566bfcd9ed137a1176c63077932eff7f3d8f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b988bff54ae0044a2754dc404a9314655b1912da7c5a4450c013f038f03c366a 0.600000000000 1410531 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": 951733, "vin": [ { "gen": { "height": 951723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b988bff54ae0044a2754dc404a9314655b1912da7c5a4450c013f038f03c366a" } } ], "extra": [ 1, 53, 37, 122, 19, 181, 38, 196, 183, 33, 220, 94, 62, 229, 116, 86, 107, 252, 217, 237, 19, 122, 17, 118, 198, 48, 119, 147, 46, 255, 127, 61, 143, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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