Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35b368f8726d7625f6030b73440a7d7712ab4def8ef7693b5694d5fba4d88b1f

Tx prefix hash: b92fbe956df512709dbe6a2e94e84ff0496f43d1ce112b5412901d068b5784b6
Tx public key: 028b8e16f607fea3153356165efc19eaf9b227a031fb1b0757ce45d766cda090
Timestamp: 1716516270 Timestamp [UCT]: 2024-05-24 02:04:30 Age [y:d:h:m:s]: 00:314:07:37:00
Block: 1028685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224636 RingCT/type: yes/0
Extra: 01028b8e16f607fea3153356165efc19eaf9b227a031fb1b0757ce45d766cda0900211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03d54b25023f6b07bd0f18b5b4e38018b0b2e9e0a168d2320d755cfcc9ad5989 0.600000000000 1496682 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": 1028695, "vin": [ { "gen": { "height": 1028685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03d54b25023f6b07bd0f18b5b4e38018b0b2e9e0a168d2320d755cfcc9ad5989" } } ], "extra": [ 1, 2, 139, 142, 22, 246, 7, 254, 163, 21, 51, 86, 22, 94, 252, 25, 234, 249, 178, 39, 160, 49, 251, 27, 7, 87, 206, 69, 215, 102, 205, 160, 144, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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