Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed378af68210007cce92659f9f7d718fbc544acbb5baa5dd63ded28b4c8f8b65

Tx prefix hash: 04f666963eb4b32620ab3db7db727f13f35c10f246d903bebb53a6ca8350485f
Tx public key: a91e62b22d1a284c2d4eee3d429894330d0dca004a1d8c3d6f6337a44299c157
Timestamp: 1719918383 Timestamp [UCT]: 2024-07-02 11:06:23 Age [y:d:h:m:s]: 00:347:11:38:37
Block: 1056880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248255 RingCT/type: yes/0
Extra: 01a91e62b22d1a284c2d4eee3d429894330d0dca004a1d8c3d6f6337a44299c1570211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 188f75f345e465629e0ab0cd6d82d40a8a870880a05ae7b6c42291b420516333 0.600000000000 1527309 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": 1056890, "vin": [ { "gen": { "height": 1056880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "188f75f345e465629e0ab0cd6d82d40a8a870880a05ae7b6c42291b420516333" } } ], "extra": [ 1, 169, 30, 98, 178, 45, 26, 40, 76, 45, 78, 238, 61, 66, 152, 148, 51, 13, 13, 202, 0, 74, 29, 140, 61, 111, 99, 55, 164, 66, 153, 193, 87, 2, 17, 0, 0, 0, 2, 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