Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b5096b995ada628072f038c46339fcf43d21e9e5e980608c23eb3c117abc174

Tx prefix hash: c8ed376e695916499a95841c449df4b8cbed2a968ef82f989301d339503ce124
Tx public key: ef33c38bafc8b2a530f5ae20791cc58a6fae9ad65b4903817e6f0f77fdab9195
Timestamp: 1728558542 Timestamp [UCT]: 2024-10-10 11:09:02 Age [y:d:h:m:s]: 01:034:00:57:30
Block: 1128510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282708 RingCT/type: yes/0
Extra: 01ef33c38bafc8b2a530f5ae20791cc58a6fae9ad65b4903817e6f0f77fdab919502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1c30f3a60284265b241fbaedc80e7f9e53bddb5ea667da0f737796aa94ceb0f 0.600000000000 1611329 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": 1128520, "vin": [ { "gen": { "height": 1128510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1c30f3a60284265b241fbaedc80e7f9e53bddb5ea667da0f737796aa94ceb0f" } } ], "extra": [ 1, 239, 51, 195, 139, 175, 200, 178, 165, 48, 245, 174, 32, 121, 28, 197, 138, 111, 174, 154, 214, 91, 73, 3, 129, 126, 111, 15, 119, 253, 171, 145, 149, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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