Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6be99fc4327db2b7880c4d455f0998fe529dfc737e907725964e96b786846a2

Tx prefix hash: 2a86ae4afd2618858a9d8945ae4544bceca92d88ac41b933cf2addae8f6e3a05
Tx public key: c1a7b6af438f7b5323eaf034e376b42cc60fc3f06eb0bc3318dc3497c8afa7d2
Timestamp: 1723020297 Timestamp [UCT]: 2024-08-07 08:44:57 Age [y:d:h:m:s]: 00:233:18:12:26
Block: 1082588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166962 RingCT/type: yes/0
Extra: 01c1a7b6af438f7b5323eaf034e376b42cc60fc3f06eb0bc3318dc3497c8afa7d2021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8facfebc18acadb95bdaa887a4b3eb2a986b77d6a4d3804972827fcbd89d6542 0.600000000000 1556417 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": 1082598, "vin": [ { "gen": { "height": 1082588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8facfebc18acadb95bdaa887a4b3eb2a986b77d6a4d3804972827fcbd89d6542" } } ], "extra": [ 1, 193, 167, 182, 175, 67, 143, 123, 83, 35, 234, 240, 52, 227, 118, 180, 44, 198, 15, 195, 240, 110, 176, 188, 51, 24, 220, 52, 151, 200, 175, 167, 210, 2, 17, 0, 0, 0, 4, 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