Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6be2ba36b454001902a60c34704c3a93c330d9e3e3ab27387aa0a88bc335037

Tx prefix hash: 6b647f7414dbcea4921fe5bbcc8d87445d5f055d736fc5582a32bc2b34513246
Tx public key: e932ba8b194791d1cc1e892bb91a78b23482fe90c3fabe5f1d927c0f095a6a7a
Timestamp: 1713553190 Timestamp [UCT]: 2024-04-19 18:59:50 Age [y:d:h:m:s]: 00:262:06:06:45
Block: 1004087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187733 RingCT/type: yes/0
Extra: 01e932ba8b194791d1cc1e892bb91a78b23482fe90c3fabe5f1d927c0f095a6a7a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eeb0bd777b0613dd1a1cbc7049dad2d5a6384634ff492792d535a6cc8b90298 0.600000000000 1464653 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": 1004097, "vin": [ { "gen": { "height": 1004087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eeb0bd777b0613dd1a1cbc7049dad2d5a6384634ff492792d535a6cc8b90298" } } ], "extra": [ 1, 233, 50, 186, 139, 25, 71, 145, 209, 204, 30, 137, 43, 185, 26, 120, 178, 52, 130, 254, 144, 195, 250, 190, 95, 29, 146, 124, 15, 9, 90, 106, 122, 2, 17, 0, 0, 0, 2, 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