Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3d35468a7b7752dd6940ffd1e46d324e9a382995638cb32a418e2d00660d361

Tx prefix hash: fead22ed06daa3a3b5fb60afa0b74a4375fa7669b6bb6771b3dcde66814ef261
Tx public key: 6eb777df5a7d2ed64497718eb21375afa1d5dc48f39f1a9714dd6beddc710c5b
Timestamp: 1707686253 Timestamp [UCT]: 2024-02-11 21:17:33 Age [y:d:h:m:s]: 00:315:08:55:20
Block: 955464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225816 RingCT/type: yes/0
Extra: 016eb777df5a7d2ed64497718eb21375afa1d5dc48f39f1a9714dd6beddc710c5b0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8b6f0dcec808f7a89bc223db77477646f61c5d3b4476a71a870dfb19827df41 0.600000000000 1414752 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": 955474, "vin": [ { "gen": { "height": 955464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8b6f0dcec808f7a89bc223db77477646f61c5d3b4476a71a870dfb19827df41" } } ], "extra": [ 1, 110, 183, 119, 223, 90, 125, 46, 214, 68, 151, 113, 142, 178, 19, 117, 175, 161, 213, 220, 72, 243, 159, 26, 151, 20, 221, 107, 237, 220, 113, 12, 91, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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