Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd2c3b6a6ec69aaf8c61ac4b04517c2da92dd96b817b1a72b74247d61bad4292

Tx prefix hash: 9bd75f1b45b045a03767930b8366af3098eb8fc928d08514fa1fe884d94cef01
Tx public key: f0b4c2e26f3bd9386a46e929aaea53539e7d2c0f8b62391411a4c565f80199ee
Timestamp: 1724412980 Timestamp [UCT]: 2024-08-23 11:36:20 Age [y:d:h:m:s]: 00:224:12:03:46
Block: 1094159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160296 RingCT/type: yes/0
Extra: 01f0b4c2e26f3bd9386a46e929aaea53539e7d2c0f8b62391411a4c565f80199ee021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a130d1c8953a17146238402679abb2b709099f147242364fa5976322f94f301 0.600000000000 1569246 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": 1094169, "vin": [ { "gen": { "height": 1094159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a130d1c8953a17146238402679abb2b709099f147242364fa5976322f94f301" } } ], "extra": [ 1, 240, 180, 194, 226, 111, 59, 217, 56, 106, 70, 233, 41, 170, 234, 83, 83, 158, 125, 44, 15, 139, 98, 57, 20, 17, 164, 197, 101, 248, 1, 153, 238, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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