Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ecf7309dc28eb98b2b292d34cf770ef2f9e23ab9f2973b9adecb16272195b28

Tx prefix hash: 8cfc7b7d5e982501b1b4243691e38543a1062644e220d82ed01c72dd7f26d885
Tx public key: edd7bb186efdeb78faec4bac1c20d7e1db37951a7d69ce5f5a25abc629c28c6e
Timestamp: 1716638657 Timestamp [UCT]: 2024-05-25 12:04:17 Age [y:d:h:m:s]: 00:187:00:25:17
Block: 1029698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133857 RingCT/type: yes/0
Extra: 01edd7bb186efdeb78faec4bac1c20d7e1db37951a7d69ce5f5a25abc629c28c6e02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f03e25460a2c5d878a01681cd7ecbdf3fbb4cf775f0c913ea1ffd145e7bcfdd0 0.600000000000 1497859 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": 1029708, "vin": [ { "gen": { "height": 1029698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f03e25460a2c5d878a01681cd7ecbdf3fbb4cf775f0c913ea1ffd145e7bcfdd0" } } ], "extra": [ 1, 237, 215, 187, 24, 110, 253, 235, 120, 250, 236, 75, 172, 28, 32, 215, 225, 219, 55, 149, 26, 125, 105, 206, 95, 90, 37, 171, 198, 41, 194, 140, 110, 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