Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26d235ad07b3b838ef017fe1dd74043dad4bc11965c08e76e87254a421941066

Tx prefix hash: 897c583271a0a95f3f59129fcdf7bac1cc7deed68b986cd24562e274256db85e
Tx public key: c22772188a32905adfbfa161f3fc8d54c1aef81023a9d9471d7136abdf801e4a
Timestamp: 1717136764 Timestamp [UCT]: 2024-05-31 06:26:04 Age [y:d:h:m:s]: 00:303:23:28:16
Block: 1033825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217238 RingCT/type: yes/0
Extra: 01c22772188a32905adfbfa161f3fc8d54c1aef81023a9d9471d7136abdf801e4a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2c4bb863aa0f0bbfd4bd67f86b4ae97015f3ad7f17bb1de1b144282d2c57ee2 0.600000000000 1502298 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": 1033835, "vin": [ { "gen": { "height": 1033825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2c4bb863aa0f0bbfd4bd67f86b4ae97015f3ad7f17bb1de1b144282d2c57ee2" } } ], "extra": [ 1, 194, 39, 114, 24, 138, 50, 144, 90, 223, 191, 161, 97, 243, 252, 141, 84, 193, 174, 248, 16, 35, 169, 217, 71, 29, 113, 54, 171, 223, 128, 30, 74, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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