Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4d4677481355cb5d6fd702af04d9daa3a210ee67439b4eba4c5da06a672267b

Tx prefix hash: 26b7c693267ad9efd8a4543bffc7cb60bb8ef1681b2c9faebeefa33e4d95ff76
Tx public key: 9839165fb48b6a8e904d438a245f62f0542217c817f8208eb8d6f141cd30a851
Timestamp: 1716507987 Timestamp [UCT]: 2024-05-23 23:46:27 Age [y:d:h:m:s]: 00:244:15:41:20
Block: 1028615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175044 RingCT/type: yes/0
Extra: 019839165fb48b6a8e904d438a245f62f0542217c817f8208eb8d6f141cd30a85102110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41381446cd63d4e1ff921b5b96476a092ff8522ae81192f3c7acad53dcb96777 0.600000000000 1496610 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": 1028625, "vin": [ { "gen": { "height": 1028615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41381446cd63d4e1ff921b5b96476a092ff8522ae81192f3c7acad53dcb96777" } } ], "extra": [ 1, 152, 57, 22, 95, 180, 139, 106, 142, 144, 77, 67, 138, 36, 95, 98, 240, 84, 34, 23, 200, 23, 248, 32, 142, 184, 214, 241, 65, 205, 48, 168, 81, 2, 17, 0, 0, 0, 4, 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